- 
                Notifications
    You must be signed in to change notification settings 
- Fork 2
chore(module): rename containers to support integrity checks #1432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(module): rename containers to support integrity checks #1432
Conversation
| Workflow has started. The target step completed with status: cancelled. | 
| Workflow has started. The target step completed with status: failure. | 
| Workflow has started. The target step completed with status: cancelled. | 
| Workflow has started. The target step completed with status: failure. | 
| Workflow has started. The target step completed with status: failure. | 
| Workflow has started. The target step completed with status: failure. | 
b308028    to
    5516243      
    Compare
  
    | Workflow has started. The target step completed with status: failure. | 
| Workflow has started. The target step completed with status: success. | 
20ac74b    to
    34131b0      
    Compare
  
    a8cc837    to
    8613738      
    Compare
  
    The base branch was changed.
| Workflow has started. The target step completed with status: success. | 
Images with pre-created mount points: - cdi-apiserver - cdi-cloner - cdi-controller - cdi-importer - cdi-operator - dvcr - dvcr-importer - dvcr-uploader - kube-api-rewriter - virt-api - virt-controller - virt-handler - virt-launcher - virt-operator - virtualization-api - virtualization-audit - virtualization-controller - hp pods Some notes: - Create /var/run subdirectories in /run, as /var/run is a symlink to ../run. - Add /var, /run and symlink /var/run -> ../run in 'distroless' base image. - Pre-create /var, /run and symlink /var/run -> ../run in kube-api-rewriter image. - Remove unused extraheaders settings in dvcr-importer and dvcr-uploader. Signed-off-by: YuryLysov <[email protected]> Co-authored-by: Ivan Mikheykin <[email protected]> Co-authored-by: Nikita Korolev <[email protected]> Signed-off-by: Nikita Korolev <[email protected]> Signed-off-by: Ivan Mikheykin <[email protected]>
1. Rename containers of kubevirt Pods, cdi Pods and dvcr Pods created in non-system namespaces (namespaces without d8- prefix). 2. Mount container-disk binary into /var/run in container with user uploaded image (support attaching cvi, vi to vm). Related PRs: deckhouse/3p-kubevirt#19 deckhouse/3p-containerized-data-importer#17 Signed-off-by: Ivan Mikheykin <[email protected]>
8613738    to
    8d9d3d1      
    Compare
  
    | /backport v1.0 | 
| Cherry pick PR 1483 to the branch release-1.0 successful! | 
Description
Rename containers of kubevirt Pods, cdi Pods and dvcr Pods created in non-system namespaces (namespaces without the
d8-prefix).Mount container-disk binary into /var/run in container with user uploaded image (support attaching cvi, vi to vm).
Related PRs:
deckhouse/3p-kubevirt#19
deckhouse/3p-containerized-data-importer#17
#1343
Why do we need it, and what problem does it solve?
Support containerd integrity checking for system images.
What is the expected result?
Checklist